|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 3060 (2001)
|
|
Title:
|
Policy Core Information Model - Version 1 Specification, February 2002.
|
|
|
2.
|
Status of approval:
|
|
|
The referred RFCs were approved by IESG (Internet Engineering Steering Group).
|
|
3.
|
Justification for the specific reference:
|
|
|
The DPI policy rule information modeling may serve [IETF RFC 3060] as baseline.See cluase 7.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/. Specifically: https://datatracker.ietf.org/ipr/search/?option=rfc_search&rfc_search=3060
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
The status of all the referred RFCs is "Proposed Standard".
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
The status of all the referred RFCs is "Proposed Standard".
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
References within the referenced RFCs are listed under item (8).
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[1] Distributed Management Task Force, Inc., "DMTF Technologies: CIM/
Standards CIM Schema: Version 2.4", available via links on/
the following DMTF web page:http://www.dmtf.org/spec/cim_schema_v24.html./
/
[2] Distributed Management Task Force, Inc., "Common Information/
Model (CIM) Specification, version 2.2, June 1999. This/
document is available on the following DMTF web page:/
http://www.dmtf.org/spec/cims.html./
/
[3] Bradner, S., "Key words for use in RFCs to Indicate Requirement/
Levels", BCP 14, RFC 2119, March 1997./
/
[4] Hovey, R. and S. Bradner, "The Organizations Involved in the/
IETF Standards Process", BCP 11, RFC 2028, October 1996./
/
[5] J. Strassner and S. Judd, "Directory-Enabled Networks", version/
3.0c5 (August 1998). A PDF file is available at/
http://www.murchiso.com/den/#denspec./
/
[6] J. Strassner, policy architecture BOF presentation, 42nd IETF/
Meeting, Chicago, Illinois, October, 1998. Minutes of this BOF/
are available at the following location:/
http://www.ietf.org/proceedings/98aug/index.html./
/
[7] Yergeau, F., "UTF-8, a transformation format of ISO 10646", RFC/
2279, January 1998./
/
[8] Levi, D. and J. Schoenwaelder, "Definitions of Managed Objects/
for Scheduling Management Operations", RFC 2591, May 1999./
/
[9] Yavatkar, R., Pendarakis, D. and R. Guerin, "A Framework for/
Policy-based Admission Control", RFC 2753, January 2000./
/
[10] Dawson, F. and D. Stenerson, "Internet Calendaring and/
Scheduling Core Object Specification (iCalendar)", RFC 2445,/
November 1998./
/
[11] Strassner, J., and E. Ellesson, B. Moore, R. Moats, "Policy Core/
LDAP Schema", Work in Progress./
/
[12] Shirey, R., "Internet Security Glossary", FYI 36, RFC 2828, May 2000./
|
|
9.
|
Qualification of
ISOC/IETF:
|
|
|
9.1-9.6 Decisions of ITU Council to admit ISOC to participate in the work of the Sector (June 1995 and June 1996).
9.7 The Internet Engineering Steering Group (IESG) is responsible for ongoing maintenance of the RFCs when the need arises. Comments on RFCs and corresponding changes are accommodated through the existing standardization process.
9.8 Each revision of a given RFC has a different RFC number, so no confusion is possible. All RFCs always remain available on-line. An index of RFCs and their status may be found in the IETF archives at http://www.rfc-editor.org/rfc.html.
|
|
10.
|
Other (for any supplementary information):
|
|
|
The referred IETF RFCs are available on the web.
[1] IETF RFC 3060 - Policy Core Information Model - Version 1 Specification: available at "http://www.ietf.org/rfc/rfc3060.txt"
|
|
